Thanks for your reply. I'm not a programmer so it is difficult to modify source to support SysvINIT. so I made and used a init script for veyon as follow: . /etc/init.d/functions prog_path=/usr/bin prog1=veyon-service prog2=veyon-server userid=awk -F ':' '{if($3==500) print $1}' /etc/passwd case "$1" in start) sudo -u $userid $prog_path/$prog1 & sudo -u $userid $prog_path/$prog2 & ;; stop) killproc $prog_path/$prog1 1>>/dev/null 2>>/dev/null killproc $prog_path/$prog2 1>>/dev/null 2>>/dev/null ;; status) status "veyon-service" status "veyon-server" ;; *) gprintf "Usage: %s {start|stop|status}\n" "$0" exit 1 ;; esac exit 0

Hello @fred are you using access control rules? If so, which conditions are enabled/used? It's true that we have a fix in 4.1.5 which will prevent Veyon from using any groups at all for access control if the LDAP/AD group member attribute is not configured or the user object could not be queried from a user login name. So first of all please check your LDAP/AD settings and perform all integration tests.

Hi @kalera15 the maximum interval is 60 seconds. Increasing this value above 10 seconds won't reduce the load on clients notably and will more likely cause timeout problems.

good evening I encountered a crash of acrobat reader dc when the 32bits version of veyon is installed on a windows 7 64 bits ... but   only when a user is logged in, if it is an administrator no worries ... I installed the 64bits version of veyon on the same computer, and acrobat reader DC works whatever the logged in user Fred

I had the same problem. You need to check another setting in the DHCP. In windows server, in your DHCP, select your scope and go to the properties. Select the DNS tab and activate the dynamic update DNS with this setting: Always update PTR and A DNS. On Veyon, you can use the computer's names without IP address. (i don't use DNS suffix) (Same thing in french) J'ai eu le même problème, tu auras besoin de vérifier les paramètres du DHCP. Sur Windows server, dans la console DHCP, sélectionne ton étendue et va sur les propriétés. Choisis l'onglet DNS et active les mises à jour dynamiques DNS avec les paramètres: Toujours mettre à jour dynamiquement les enregistrements PTR et A DNS. Sur Veyon, tu peux utiliser les noms des ordinateurs sans les adresses IP (je n'utilise pas le suffixe DNS) Yohann

Any movement on this? My students have figured out to move their non-school windows to their second screen... I'm using v. 4.1.5 We have the dual screen box checked in the configurator. TomT

I have successfully installed it but when I click veyon master or configurator nothing happens What is the solution?

Thanks for providing the investigations and sharing the workaround! While scrutinizing the issue I spotted a problem in the build system leading to relevant x11vnc features such as the keyboard extension not being enabled at compile time. This will be fixed in 4.1.6.

Unfortunately we have to postpone this feature in order to get everything else done for 4.2.

Welcome to Veyon! Unfortunately it's currently not possible. We could implement this through professional services. Please contact support@veyon.io this could be an option for you.

Restricting access to a group such as teacher is the way to go so there seems to be a problem with the system or Veyon configuration. I assume the teacher users are member of a teacher group on both master and all client computers? Can you run getent group teacher and post the output here?

Please switch to the 4.1 branch or install cyrus-sasl-mingw-w64.

Have you solved the problem by now? Please see https://docs.veyon.io/en/latest/admin/configuration.html#authentication for more information on how to set up authentication in Veyon.

Ich arbeite mit windows 7 64bit

Hi Tobias, I just described a similar issue here: [https://github.com/veyon/veyon/issues/455](link url) Thanks in advance, Julius

Ok, As this rooms PCs are windows PCs, joined to an Active Directory, I used AD, and auth works fine (because my organization's AD master did it with me). I guess I needed some more configuration in env and advanced parameters to make it work. I didn't have to do that with linux, as my PCs were LDAP auth based, and in access control, I just had to choose "default (local groups and users)", and not LDAP, as I have to with AD joined windows PCs. I didn't test further ldap conf, as I finally don't need it Answer this post could help other people with the same question, though